Method and device for transmitting data

ABSTRACT

Embodiments of the present application provide a method and a device for transmitting data, which are capable of achieving timely data transmission. The method includes: starting, by a receiving end, a timer of a first delivery mode when determining that data delivered and data to be delivered are not continuous, where the first delivery mode is used to indicate that the receiving end directly delivers data to an upper layer upon the receipt of the data; and delivering, the receiving end, the data to be delivered to the high level using the first delivery mode in a case where the timer of the first delivery mode does not expire.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. patent applicationSer. No. 16/713,948, filed on Dec. 13, 2019, which is a continuation ofInternational Application No. PCT/CN2018/077052, filed on Feb. 23, 2018,which claims priority to PCT patent application PCT/CN2017/088515, filedon Jun. 15, 2017 and entitled “Method and Device for Transmitting Data”.All contents of these applications are incorporated by reference hereinin their entireties.

TECHNICAL FIELD

The present application relates to the field of communications, and,more particularly, to at method and a device for transmitting data.

BACKGROUND

In a Long Term Evolution (LTE) system, a Radio Link Control (RLC) entitydelivers data to a Packet Data Convergence Protocol (PDCP) layer inorder, that is, a Service Data Unit (SDU) n must be delivered to thePDCP layer before an SDU n+1.

However, in a New Radio (NR) system, in some cases, there is no need todeliver in order. Therefore, a new delivery manner is needed to meet theneeds of different scenarios.

SUMMARY

Embodiments of the present application provides a method and a devicefor transmitting data, which are capable of achieving data delivery toan upper layer in real-time.

In a first aspect, a method for transmitting data is provided,including:

starting, by a receiving end, a timer of a first delivery mode whendetermining that delivered data and data to be delivered are notcontinuous, where the first delivery mode is used to indicate that thereceiving end directly delivers data to an upper layer upon receipt ofthe data; and

delivering, by the receiving end, the data to be delivered to the upperlayer using the first delivery mode when the timer of the first deliverymode does not expire.

Therefore, in the case where the delivered data and the data to bedelivered are not continuous, the receiving end may deliver data to theupper layer using the first delivery mode by starting the timer of thefirst delivery mode. In the first delivery mode, after receiving thedata, the receiving end does not need to save discontinuous data in areceiving buffer, but can directly deliver the data to the upper layer,which is capable of achieving timely data delivery, and in the firstdelivery mode, it does not need to use the receiving buffer, thus savingsystem resources.

In conjunction with the first aspect, in some implementations of thefirst aspect, the method further includes:

stopping, by the receiving end, the timer of the first delivery modewhen determining that the delivered data and the data to be deliveredare continuous, if the timer of the first delivery mode is running.

That is, when the timer of the first delivery mode is in a non-operatingstate, a start condition of the timer of the first delivery mode may bethat the data to be delivered and the delivered data are not continuous;when the first delivery mode timer is in an operating state, the stopcondition of the timer of the first delivery mode may be that the datato be delivered and the delivered data are continuous.

In conjunction with the first aspect, in some implementations of thefirst aspect, the method further includes:

determining, by the receiving end, whether the delivered data and thedata to he delivered are continuous according to window information of areordering window and information of the delivered data.

In conjunction with the first aspect, in some implementations of thefirst aspect, the window information of the reordering window includes awindow lower bound identification of the reordering window, and thedetermining, by the receiving end, whether the delivered data and thedata to be delivered are continuous according to the window informationof the reordering window and the information of the delivered data,includes:

determining, by the receiving end, whether the delivered data and thedata to be delivered are continuous according to the window lower boundidentification of the reordering window and a serial number SN of a lastdelivered service data unit SDU.

In some embodiments, the window lower bound. identification of thereordering window may be a Sequence Number (SN) of a next PDU waiting tobe received, or a next SN of a highest SN in the received PDU, if a SNof a data packet is smaller than the window lower bound of thereordering window, that is, the SN of the data packet is outside thereordering window, then the data packet can be considered as having beensuccessfully received and delivered to the upper layer, and the windowupper bound identification of the window can be the window lower boundidentification+window size.

Therefore, the window lower bound identification of the reorderingwindow can indicate information of the data to be delivered, forexample, a minimum SN of the data to be delivered, so that the receivingend judges, according to the minimum SN of the data to he delivered anda maximum SN of the delivered data, whether the two are continuous, soas to determine whether the data to be delivered and the delivered dataare continuous.

In conjunction with the first aspect, in some implementations of thefirst aspect, the determining, by the receiving end, whether thedelivered data and. the data to be delivered are continuous according tothe window lower hound identification of the reordering window and theserial number SN of the last delivered service data unit SDU, includes:

determining that the delivered data and the data to be delivered are notcontinuous if a count value corresponding to the window lower boundidentification is not equal to a count value corresponding to a next SNof the SN of the last delivered SDU; or

determining that the delivered data and the data to be delivered arecontinuous if the count value corresponding to the window lower boundidentification is equal to the count value corresponding to the next SNof the SN of the last delivered SDU.

Here, the count value corresponding to the next SN of the SN of the SDUmay be the SN of the last delivered data, plus one, and then bedetermined in conjunction with RX_HFN.

In conjunction with the first aspect, in some implementations of thefirst aspect, the method further includes:

setting a window lower bound identification of a reordering window to acount value corresponding to an SDU that is expected to be deliverednext time when the timer of the first delivery mode is in an expiredstate.

Here, the count value corresponding to the SDU that is expected to bedelivered next time may be the SN that is expected to be delivered nexttime, and be determined in conjunction with RX_HFN.

In conjunction with the first aspect, in some implementations of thefirst aspect, the receiving end starts a timer of the first deliverymode when determining that the delivered data. and the data to bedelivered are not continuous, includes:

starting the timer of the first delivery mode when the count valuecorresponding to the SDU that is expected to be delivered next time isnot equal to the count value corresponding to the last delivered SDU.

In conjunction with the first aspect, in some implementations of thefirst aspect, the receiving end is a terminal device or a networkdevice.

In conjunction with the first aspect, in some implementations of thefirst aspect, the receiving end is a terminal device, and the methodfurther includes:

receiving, by the receiving end, indication information sent by anetwork device, where the indication information is used to indicatethat the terminal device delivers data to the upper layer using thefirst delivery mode or a second delivery mode, where the second deliverymode is used to indicate that the receiving, end delivers data to theupper layer in order.

In some embodiments, the indication information is specificallyconfigured to indicate that a packet data convergence protocol PDCPlayer of the terminal device delivers data to the upper layer using thefirst, delivery mode or the second delivery mode.

In some embodiments, the indication information is specificallyconfigured to indicate that a radio link control RLC layer of theterminal device delivers data to the upper layer using the firstdelivery mode or the second delivery mode.

In conjunction with the first aspect, in some implementations of thefirst aspect, the receiving, by the receiving end, the indicationinformation sent by the network device, includes:

receiving, by the receiving end, a radio resource control RRC signalingsent by the network device, where the radio resource control signalingincludes the indication information.

In conjunction with the first aspect, in some implementations of thefirst aspect, the receiving, by the receiving, end, the indicationinformation sent by the network device, including:

receiving, by the receiving end, a media access control MAC controlelement CE Gar a packet data convergence protocol PDCP control protocoldata unit PDU, sent by the network device, where the MAC CE or PDCPcontrol PDU includes the indication information,

In a second aspect, a method for transmitting data is provided,including:

setting, by a receiving end, a duration of a timer of a second deliverymode to zero when determining that data is delivered to an upper layerusing a first delivery mode;

delivering, by the receiving end, data to be delivered to the upperlayer using the first delivery mode;

where the first delivery mode is used to indicate that the receiving enddirectly delivers data to the upper layer upon receipt of the data, andthe second delivery mode is used to indicate that the receiving enddelivers data to the upper layer in order.

In a third aspect, a device for transmitting data is provided,including:

receiving, by a terminal device, indication information sent by anetwork device, where the indication information is used to indicatethat a packet data convergence protocol PDCP layer and a radio linkcontrol RLC layer of the terminal device deliver data to an upper layerusing a first delivery mode or a second delivery mode, where the firstdelivery mode is used to indicate that the terminal device directlygenerates service data unit SDU data and deliver the SDU data to theupper layer upon receipt of protocol data unit PDU data, and the seconddelivery mode is used to indicate that the terminal device delivers datato the upper layer in order; and deliver the SDU data to the upper layeraccording to the indication information.

In a fourth aspect, a device for transmitting data is provided,including a unit for executing the methods according to the first aspector any optional implementation of the first aspect as such.

In a fifth aspect, a device for transmitting data is provided, includinga unit for executing the methods according to the second aspect or anyoptional implementation of the second aspect as such.

In a sixth aspect, a device for transmitting data is provided, includinga unit for executing the methods according to the third aspect or anyoptional implementation of the third aspect as such.

In a seventh aspect, a device for transmitting data is provided,including a memory, a processor and a transceiver; the memory isconfigured to store programs, and the processor is configured to executethe programs, and when the programs are executed, the processor executesthe methods according to the first aspect or any optional implementationof the first aspect as such based on the transceiver.

In an eighth aspect, a device for transmitting data is provided,including a memory, a processor and a transceiver; the memory isconfigured to store programs, and the processor is configured to executethe programs, and when the programs are executed, the processor executesthe methods according to the second aspect or any optionalimplementation of the second aspect as such based on the transceiver.

In a ninth aspect, a device for transmitting data is provided, includinga memory; a processor and a transceiver: the memory is configured tostore programs, and the processor is configured to execute the programs,and when the programs are executed, the processor executes the methodsaccording to the third aspect or any optional implementation of thethird aspect as such based on the transceiver.

In a tenth aspect, a computer readable medium is provided, the computerreadable medium stores program code executed by a terminal device, andthe program code includes instructions for executing the methodsaccording to the first aspect or any optional implementation of thefirst aspect as such.

In a eleventh aspect, a computer readable medium is provided, thecomputer readable medium stores program code executed by a terminaldevice, and the program code includes instructions for executing, themethods according to the second aspect or any optional implementation ofthe second aspect as such.

In a twelfth aspect, a computer readable medium is provided, thecomputer readable medium stores program code executed by a terminaldevice, and the program code includes instructions for executing themethods according to the third aspect or any optional implementation ofthe third aspect as such.

In a thirteenth aspect, a computer program product includinginstructions is provided, which, when executed on a computer, causes thecomputer to perform the methods according to the first aspect or anyoptional implementation of the first aspect as such.

In a fourteenth aspect, a computer program product includinginstructions is provided, which, when executed on a computer, causes thecomputer to perform the methods according to the second aspect or anyoptional implementation of the second aspect as such.

In a fifteenth aspect, a computer program product including,instructions is provided, which, when executed on a computer, causes thecomputer to perform the methods according to the third aspect or anoptional implementation of the third aspect as such.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a wireless communication systemaccording to an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for transmitting dataaccording to an embodiment of the present application.

FIG. 3 is a schematic flowchart of a method for transmitting dataaccording to another embodiment of the present application.

FIG. 4 is a schematic flowchart of a method for transmitting dataaccording to still another embodiment of the present application.

FIG. 5 is a schematic block diagram of a device for transmitting dataaccording to an embodiment of the present application.

FIG. 6 is a schematic block diagram of a device for transmitting dataaccording to another embodiment of the present application.

FIG. 7 is a schematic block diagram of a device for transmitting dataaccording to still another embodiment of the present application.

FIG. 8 is a schematic block diagram of a device for transmitting dataaccording to an embodiment of the present application.

DESCRIPTION OF EMBODIMENTS

Technical solutions of the embodiments of the present application willbe described below in conjunction with the accompanying drawings.

The technical solutions of the embodiments of the present applicationmay be applied to various communication systems, such as Global Systemfor Mobile Communications (GSM) system, Code Division Multiple Access(CDMA) system, Wideband Code Division Multiple Access (WCDMA) system,General Packet Radio Service (CPRS) system, Long Term Evolution (LTE)system, LTE, Frequency Division Duplex (FDD) system, LTE Time DivisionDuplex (TDD) system, Universal Mobile Telecommunication System (UMTS),World Interoperability for Microwave Access (WiMAX) communicationsystem, the future 5G system, and the like.

FIG. 1 shows a wireless communication system 100 applied in anembodiment of the present application. The wireless communication system100 may include a network device 110. The network device 100 may be adevice that communicates with a terminal device. The network device 100may provide communication coverage for a particular geographic area andmay communicate with terminal devices (e.g., UE) located within thecoverage, in some embodiments, the network device 100 may be a BaseTransceiver Station (BTS) in a GSM system or a CDMA system, a NodeB (NB)in a WCDMA system, an Evolutional Node B (eNB or eNodeB) in a LTEsystem, or a wireless controller in a Cloud Radio Access Network (CRAN).Alternatively, the network device can be a relay station, an accesspoint, a vehicle-mounted device, a wearable device, a network-sidedevice in the future 5G network or a network device in a future evolvedPublic Land Mobile Network (PLMN), and the like.

The wireless communication system 100 further includes at least oneterminal device 120 located within the coverage of the network device110. The terminal device 120 may be mobile or stationary. In someembodiments, the terminal device 120 can refer to an access terminal, aUser Equipment (UE), a subscriber unit, a subscriber station, a mobilestation, a mobile table, a remote station, a remote terminal, a mobiledevice, a user terminal, a terminal, a wireless communication device, auser agent or a user device. The access terminal can be a cellularphone, a cordless phone, a Session Initiation Protocol (SIP) telephone,a wireless local loop (WLL) station, a personal digital assistant (PDA),a handheld device having wireless communication capability, a computingdevice or other processing devices connected to a wireless modem, avehicle-mounted device, a wearable wireless device, a terminal device infuture 5G networks or a terminal device in future evolved PLMN, and thelike.

In some embodiments, a 5G system or network can also be referred to as aNR system or network.

The following is a brief introduction to the background knowledgerelated to the embodiments of the present application.

A Radio Link Control (RLC) layer is located between a Packet DataConvergence Protocol (PDCP) layer and a Media Access Control (MAC)layer. The RLC layer communicates with the PDCP layer through a ServiceAccess Point (SAP) and the MAC layer through a logical channel. Eachlogical channel of each UE has an RLC entity. Data received by the RLCentity from the PDCP layer, or sent to the PDCP layer, is referred to asRLC SDU or PDCP PDU. Data received by the RLC entity from the MAC layer,or sent to the MAC layer, is referred to as RLC PDU or MAC SDU.

If the RLC PDU received by a receiving end (which can be a terminal or anetwork device) at a reordering window is disorderly, it needs to bereordered first and then delivered to the PDCP layer. The disorderlyarrived RLC PDU will be stored in a receiving buffer first, untilprevious RLC PDUs have been successfully received and delivered to thePDCP layer.

When receiving RLC PDU data, the receiving end needs to detect which RLCPDU has been missed. In order to avoid excessive reordering delay, areordering timer (t_Reordering) can be triggered to wait for the missedRLC PDU. Briefly, the receiving end will only wait for the RLC PDU thathas not been received for a period of time, If the RLC PDU is notreceived after the period of time, the receiving end will not continueto wait. T_reordering determines a time to wait for a PDU not received.In an existing LTE protocol, a behavior of t_Reordering is specified,that is, a start condition, a stop condition, a trigger condition, and abehavior after the trigger, and the like. in summary, the purpose oft_Reordering is to ensure that the data packets in the reordering windoware delivered to the PDCP layer in order.

However, it does not need to deliver in order for all the cases. Forexample, if the PDCP layer has an ordering capability, the disordereddata delivered by the RLC can be reordered by the PDCP layer, and thenthe RLC layer can timely deliver the received data to the PDCP layer forthe PDCP layer to process the data.

In view of this, an embodiment of the present application provides amethod for transmitting data, which provides a timely delivery mode,thereby achieving timely delivery of data from the RLC layer to the PDCPlayer.

FIG. 2 is a schematic flowchart of a method 200 for transmitting dataproposed in an embodiment of the present application, the method 200 canbe executed by the terminal device or the network device in the wirelesscommunication system shown in FIG 1. As shown in FIG. 2, the method 200includes:

S210, a receiving end starts a timer of a first delivery mode whendetermining that delivered data and data to be delivered are notcontinuous, where the first delivery mode is used to indicate that thereceiving end directly delivers data to an upper layer upon receipt ofthe data; and

S220, the receiving end delivers the data to be delivered to the upperlayer using the first delivery mode when the timer of the first deliverymode does not expire.

In the existing technology, when the delivered data and the data to bedelivered are not continuous, that is, there is a gap between thedelivered data and the data to be delivered, the receiving end willstore the data to be delivered in a buffer until data after thedelivered data and before the data to be delivered, that is data of thegap part, is successfully delivered to the upper layer, and then thedata to be delivered is delivered to the upper layer. Therefore, timelydelivery of the data to be delivered cannot be achieved.

In the embodiment of the present application, the receiving end iscapable of starting the timer of the first delivery mode when thedelivered data and the data to be delivered are not continuous, therebydelivering the data to the upper layer using the first delivery mode. Inthe first delivery mode, after receiving the data, the receiving enddoes not need to store the discontinuous data in a receiving buffer, butcan directly deliver the data to the upper layer. Therefore, in thefirst delivery mode, it does not need to use the receiving buffer, thussaving system resources,

It should be noted that the directly delivering the data to the upperlayer mentioned here may be directly delivering received. RLC PDU datato the upper layer, or reorganizing the received RLC PDU data to obtainRLC SDU, and then delivering the RLC SDU to the upper layer, The upperlayer mentioned here can be a PDCP layer, the first delivery mode canalso be referred to as a timely delivery mode, or a real-time deliverymode, and the like.

When the timer of the first delivery mode is running, or when the timerof the first delivery mode is in an operating state, the receiving endcan always use the timely delivery mode to deliver data to the upperlayer. That is, after receiving the data, it is delivered directly tothe upper layer until the timer of the first delivery mode is stopped orexpired.

When the time is longer than the duration of the timer, the timerexpires. If the time does not longer the duration of the timer, but astop condition is met, the timer is stopped. When the timer is in anexpired state or a stopped state, or when the timer is not in theoperating state, the receiving end does not deliver the data to theupper layer in the timely delivery mode, but delivers the data to theupper layer in an orderly delivery mode in the prior art.

In in some embodiments, the method 200 may further include:

the receiving end stops the timer of the first delivery mode whendetermining that the delivered data and the data to be delivered arecontinuous, if the timer of the first delivery mode is running.

Generally, a Start condition of the timer of the first delivery mode maybe that the data to be delivered and the delivered data are notcontinuous, and the stop condition of the tinier of the first deliverymode may be that the data to be delivered and the delivered data arecontinuous. That is, when the tinier of the first delivery mode is in anon-operating state, the receiving end may start the timer of the firstdelivery mode when the data to be delivered and the data delivered arenot continuous, thus delivering the data to the upper layer using thetimely delivery mode, and when the data to be delivered and thedelivered data are continuous, the receiving end may deliver the data tothe upper layer using the delivery mode in the prior art, that is, inthe orderly delivery mode.

This is, when the timer of the first delivery mode is in thenon-operating state, the start condition of the timer of the firstdelivery mode may be that the data to be delivered and the delivereddata are not continuous, and when the timer of the first delivery modeis in the operating state, the stop condition of the timer of the firstdelivery mode may be that the data to be delivered and the delivereddata are continuous.

When the timer of the first delivery mode is stopped, the receiving endresets the duration of the timer of the first delivery mode to zero, sothat the timer of the first delivery mode is in the non-operating state.When the duration of the timer of the first delivery mode is set to avalue greater than zero. the timer of the first delivery mode is startedand the timer of the first delivery mode is in the operating state. Whenthe timer of the first delivery mode is started, after receiving, datain a reordering window, the receiving end delivers the data directly tothe upper layer. Even if there is a packet loss, there is no waiting forpacket loss. As long as new data arrives, the received new data can bedelivered to the upper layer.

As an embodiment, the method 200 further includes:

the receiving end determines whether the delivered data and the data tobe delivered are continuous according to the window information of areordering window and information of the delivered data.

The window information of the reordering window may include informationof the reordering window, such as window lower bound identification,window upper bound identification and window size, and the like. Thesite of the reordering window is configured to indicate a number of PDUthat can be received without window movement.

For example, the window lower bound identification of the reorderingwindow may be a Sequence Number (SN) of a next PDU waiting to bereceived, or a next SN of a highest SN in the received PDU, if a SN of apacket is smaller than the window lower bound identification of thereordering window, that is, the SN of the data packet is outside thereordering window, then the packet can be considered as havini4 beensuccessfully received and delivered to the upper layer, and the windowupper bound identification of the window can be the window lower boundidentification+window size. For example, if a maximum SN of the receiveddata packet is 50, the window lower bound identification can be SN+1=51,and if the window size is 512, the window upper bound identification canbe 51+512=563.

In this case, the movement of the reordering window is mainly driven bythe window lower bound, that is, only when the data packet of the windowlower bound is successfully received and delivered to the upper layer,or when the reordering timer expires, the window moves backwards.Therefore, the window lower bound identification of the reorderingwindow can indicate information of the data to be delivered, Forexample, a minimum SN of the data to be delivered. In this way, thereceiving end determines, according to the minimum SN of the data to bedelivered and the maximum SN of the delivered data, whether the two arecontinuous, thereby determining whether the data to be delivered and thedelivered data are continuous.

Therefore, in the embodiment of the present application, a SN of a RLCSDU last delivered by the receiving end to the upper layer is denoted asLast_Delivered_PDCP_RX_SN. The receiving end. determines whether thedata to be delivered and the delivered data are continuous according tothe SN of the SDU last delivered to the upper layer in conjunction withthe SN indicated by the window lower bound identification of thereordering window.

Specifically, since SN has a range, when it is larger than the range, SNwill be counted again. The current Hyper Frame Number (HFN), denoted asRX_HFN, can be used to record a recount times. Therefore, according tothe SN of the last delivered SDU and in conjunction with RX_HFN, thereceiving end can determine a count value (COUNT) corresponding to thelast delivered SDU, that is, the serial number of the SDU actuallydelivered by the receiving end to an upper layer. The same method can beused to calculate the corresponding count value according to the windowlower bound identification, that is, the count value corresponding tothe minimum SN of the data to be delivered.

In some embodiments, the receiving end determines whether the delivereddata and the data to be delivered are continuous according to the windowinformation of the reordering window and the information of thedelivered data, includes:

determining that the delivered data and the data to be delivered are notcontinuous if a count value corresponding to the window lower boundidentification is not equal to a count value corresponding to a next SNof the SN of the last delivered SDU; or

determining that the delivered data and the data to be delivered arecontinuous if the count value corresponding to the window lower boundidentification is equal to the count value corresponding to the next SNof the SN of the last delivered SDU.

The count value corresponding to the window lower bound identificationcan reflect an actual serial number value of the data to be delivered,and the count value corresponding to the SN of the last delivered SDUcan reflect an actual serial number value of the last delivered SDU. Bycomparing whether the two count values are continuous, it can bedetermined whether the delivered data and the data to be delivered arecontinuous. For example, the count value corresponding to the windowlower bound identification is COUNT1, and the count value correspondingto the SN of the last delivered SDU is COUNT2. If COUNT1=COUNT2+1, thenit can be determined that the delivered data and the data to bedelivered are continuous, otherwise, it is determined. that thedelivered data and the data to be delivered are not continuous.

It should be understood that, in a specific implementation, the windowlower bound identification may be set as the SN of the last deliveredSDU. When performing such comparison, it can be determined that thedelivered data and the data to be delivered are not continuous when thecount value corresponding to the window lower bound identification isnot equal to the count value corresponding to the SN of the lastdelivered SDU, and it can be determined that the delivered data and thedata to be delivered are continuous when the count value correspondingto the window lower bound identification is equal to the count valuecorresponding, to the SN of the last delivered SDU. That is, diespecific judgment condition can be adjusted according to a definition ofthe window lower bound identification, which is not specifically limitedby the embodiment of the present application.

As an embodiment, the method 200 further includes:

setting a window lower bound identification of a reordering window to acount value corresponding to an SDU that is expected to be deliverednext time when the timer of the first delivery mode is in an expiredstate.

The tinier of the fast delivery mode being in the expired state may beunderstood as that the timer of the first delivery mode is in thenon-operating state.

Specifically, the receiving end can set the window lower boundidentification of the reordering window to a count value correspondingto the count value corresponding to the SDU that is expected to bedelivered next time (denoted as Next_PDCP_RX_SN). For example, thereceiving end can determine the corresponding COUNT value according tothe Next_PDCP_RX_SN in conjunction with the current RX_HFN of thereceiving end. Then, when the timer of the first delivery mode is in theexpired state, the receiving end can start the timer of the firstdelivery mode when the count value corresponding to the SDU that isexpected to be delivered next time is not equal to the count valuecorresponding to the last delivered SDU, that is, when the data to bedelivered and the delivered data are not continuous, so that the datacan be data delivered to the upper layer using the timely delivery mode.

It should be understood that, in the embodiment of the presentapplication, the receiving end may be a terminal device or a networkdevice, which is not specifically limited in the embodiment of thepresent application.

If the receiving end is a terminal device, as an embodiment, the method200 may further include:

the receiving end receives the indication information sent by a networkdevice, where the indication information is used to indicate that theterminal device delivers data to the upper layer using the firstdelivery mode or a second delivery mode, where the second delivery modeis used to indicate that the receiving end delivers data to the upperlayer in order.

That is, when the receiving end is a terminal device, which deliverymode to be specifically used can be configured by the network device tothe terminal device. The network device can configure the delivery modefor the terminal device to deliver data to the upper layer according tofactors such as system requirements or upper layer processingcapabilities, and the like. For example, the network device canconfigure the terminal device to use the first delivery mode, that is,the timely delivery mode, to deliver data to the upper layer in a caseof high delay requirements, so as to reduce a delay of datatransmission. Alternatively, when the processing capability of the upperlayer is strong, the data is delivered to the upper layer using thetimely delivery mode. That is, the disordered data is delivered directlyto the upper layer and reordered by, the upper layer.

In some embodiments, the indication information is specifically used toindicate that a packet data convergence protocol PDCP layer of theterminal device delivers data to the upper layer using the firstdelivery mode or the second delivery mode.

In some embodiments, the indication information is specifically used toindicate that a radio link control RLC layer of the terminal devicedelivers data to (he upper layer using the first delivery mode or thesecond delivery mode.

That is, the indication information for indicating the delivery modeused by the RLC layer of the terminal device and the indicationinformation for indicating the delivery mode used by the PDCP layer ofthe terminal device can be carried in a same indication domain. Forexample, they may be carried in a specific indication domain of RRCsignaling or dynamic signaling. That is, the same indication informationmay be used to indicate which delivery mode is used by the RLC layer andPDCP layer of the terminal device.

As an embodiment, the receiving end receives the indication informationsent by the network device, includes:

the receiving end receives a radio resource control RRC signaling sentby the network device, where the radio resource control signalingincludes the indication information.

That is, the network device may semi-statically configure which deliverymode to be used for the receiving end through the RRC signaling.

As another embodiment, the receiving end receives the indicationinformation sent by the network device, includes:

the receiving end receives a media access control MAC control element CEor a packet data convergence protocol PDCP control protocol data unit(PDU), sent by the network device, where the MAC CE or PDCP control PDUincludes the indication information.

That is to say, the network device can dynamically configure whichdelivery mode the terminal device uses to deliver data to the upperlayer through a dynamic signaling, for example, MAC CE or PDCP controlPDU.

In some embodiments, the network device can also, send the indicationinformation to the receiving end in other ways, and the embodiment ofthe present application does not limit the specific notification mode ofthe indication information.

Therefore, in the method for transmitting data in the embodiment of thepresent application, the receiving end can start the timer of the timelydelivery mode when the data to be delivered and the delivered data arenot continuous, so as to realize timely delivery of data to the upperlayer, which is conducive to realize timely data delivery and reduce thedelay of data transmission.

It should be noted that, in the embodiment of the present application,no matter which delivery mode is used, when the receiving end receivesthe Protocol Data Unit (PDU) data, it needs to perform de-header (ordecapsulation) processing on the PDU data to generate SDU data, and thenthe SDU data can be delivered to the upper layer. The process ofgenerating SDU data from PDU data is omitted for the convenience ofdescription, but it does not mean that the process is not executed.

In an embodiment of the present application, the receiving end cangenerate the SDU data according to multiple PDUs, where, multiple PDUsmay constitute a complete SDU, or may constitute part of a complete SDU.Alternatively, part of the multiple PDUs may constitute a complete. SDU.That is, the SDU data may be generated by at least one PDU, which iscapable of constituting a complete SDU, and a previous (and/orposterior) PDU of the at least one PDU.

That is, the receiving end can generate SDU data from at least one PDU,which is capable of constituting a complete SDU, and a previous PDU ofthe at least one PDU, or the receiving end may generate SDU data from atleast one PDU, which is capable of constituting a complete SDU, and aposterior PDU of the complete PDU, or the receiving end may alsogenerate an SDU data from the at least one PDU, the previous PDU of theat least one PDU, and the posterior PDU of the at least. one PDU, andthe like. The embodiment of the present application does notspecifically limit the generation mode of the SDU.

In the first delivery mode, after the SDU data is generated, thereceiving end directly delivers the SDU data to the upper layer, even ifprevious SDU data of the SDU data has not been delivered to the upperlayer. That is, the receiving end can disorderly deliver the SDU data tothe upper layer.

In the second delivery mode, after the SDU data is generated, thereceiving end needs to wait for all previous SDU data of the SDU dataare delivered to the upper layer, and then the SDU data can be deliveredto the upper layer. That is, the receiving end needs to deliver SDU datato the upper layer in order.

FIG. 3 is a schematic flowchart of a method 300 for transmitting data inanother embodiment of the present application. The method 300 can beexecuted by the terminal device or the network device in the wirelesscommunication system shown in FIG. 1. As shown in FIG. 3, the method 300includes:

S310, a receiving end sets a duration of a timer of a second deliverymode to zero; and

S320, the receiving end deliver data to be delivered to an upper layerusing a first delivery mode;

where the first delivery mode is used to indicate that the receiving enddirectly delivers the data to the upper layer upon the receipt of thedata, and the second delivery mode is used to indicate that thereceiving end delivers data to the upper layer in order.

In this embodiment, a window upper bound identification of a reorderingwindow may be a next SN number of a highest SN number in the receivedPDU. If a SN of a. data packet is larger than the window upper boundidentification of the reordering window, that is, the SN of the datapacket is outside the reordering window, then the data packet can beconsidered as having not been successfully received. lithe receiving endreceives a data packet whose SN is larger than the current window upperbound identification, then the receiving end can update the window upperbound identification as the SN of the newly received data packet, thatis, the window is moved backwards.

That is to say, the movement of the reordering window is mainly drivenby the upper bound of the window, that is, as long as the receiving endreceives a data packet with a larger SN, the window will move backwards.In this case, the receiving end only needs to set the duration of thetimer of the second delivery mode, that is, an orderly delivery mode, tozero. When the duration of the timer of the sequential delivery mode iszero, the timer is in a non-operating state. There fore, even if thereis packet loss, there is no waiting for the packet loss, so that thewindow will move backwards following receipt of a new data packet.Accordingly, when receiving a new data packet, the receiving end candirectly deliver the newly received data packet to the upper layer, thusrealizing timely delivery of the received data packet.

Therefore, in this scenario, the receiving end does not need todetermine whether the delivered data and the data to be delivered arecontinuous, as long as the duration of the timer of the second deliverymode is set to 0, the timely delivery of the received data packet can berealized. Alternatively, if the data need to be delivered in order, itonly need to set the duration of the timer of the second delivery modeto a value greater than zero. Therefore, the receiving end can switchbetween the timely delivery mode and the orderly delivery mode bycontrolling the duration of the timer of the second delivery mode.

It should be noted that, in the embodiment of the present application,no matter which delivery mode is used, when the receiving end receivesthe Protocol Data Unit (PDU) data, it needs to perform de-header (ordecapsulation) processing on the PDU data to generate Service Data Unit(SDU) data, and then the SDU data can be delivered to the upper layer.The process of generating SDU data from PDU data is omitted for theconvenience of description, but it does not mean that the process is notexecuted.

In an embodiment of the present application, the receiving end cangenerate the SDU data according to multiple PDUs, where, the multiplePDUs may constitute a complete SDU, or may constitute pact of a completeSDU. Alternatively, part of the multiple PDUs may constitute a completeSDU. That is, the SDU data may be generated by at least one PDU, whichis capable of constituting a complete SDU, and a previous (and/orposterior) PDU of the at least one PDU.

That is, the receiving end can generate SDU data from at least one PDU,which is capable of constituting a complete SDU, and a previous PDU ofthe at least one PDU, or the receiving end may generate SDU data from atleast one PDU, which is capable of constituting a complete SDU, and aposterior PDU of the complete PDU, or the receiving end may alsogenerate an SDU data from the at least one PDU, the previous PDU of theat least one PDU, and the posterior PDU of the at least one PDU, and thelike. The embodiment of the present application does not specificallylimit the generation mode of the SDU.

In the first delivery mode, after the SDU data is generated, thereceiving end directly delivers the SDU data to the upper layer, even ifprevious SDU data of the SDU data has not been delivered to the upperlayer. That is, the receiving end can disorderly deliver the SDU data tothe upper layer.

In the second delivery mode, after the SDU data is generated, thereceiving end needs to wait for all previous SDU data of the SDU dataare delivered to the upper layer, and then the SDU data can be deliveredto the upper layer. That is, the receiving end needs to deliver SDU datato the upper layer in order.

FIG. 4 is a schematic flowchart of a method 700 for transmitting data instill another embodiment of the present application. The method 700 canbe executed by the terminal device in the wireless communication systemshown in FIG. 1. As shown in FIG. 4, the method 700 includes:

S710, a terminal device receives indication information sent by anetwork device, where the indication information is used to indicatethat a packet data convergence protocol PDCP layer and a radio linkcontrol RLC layer of the terminal device deliver data to an upper layerusing a first delivery mode or a second delivery mode, where the firstdelivery mode is used to indicate that the terminal device directlygenerates service data unit SDU data and deliver the SDU data to theupper layer upon receipt of PDU data, and the second delivery mode isused to indicate that the terminal device delivers data to the upperlayer in order; and

S720, deliver the SDU data to the upper layer according to theindication information.

Therefore, in the embodiment of the present application, the indicationinformation for indicating the delivery mode used by the RLC layer ofthe terminal device and the indication information for indicating thedelivery mode used by the PDCP layer of the terminal device can becarried in a same indication domain. For example, they may be carried ina specific indication domain of RRC signaling or dynamic signaling,.That is, the same indication information may be used to indicate whichdelivery mode is used by the RLC layer and PDCP layer of the terminaldevice. It should be understood that, no matter which delivery mode isused, upon receipt of the PDU data, the receiving end needs to performde-header processing on the PDU data to generate the SDU data, and thenthe SDU data can be delivered to the upper layer.

In the embodiment of the present application, the receiving end mayreceive multiple PDUs, and the receiving end may perform de-headerprocessing on the multiple PDUs to generate an SDU, where, the multiplePDUs may constitute a complete SDU, or may constitute part of a completeSDU. Alternatively, pan of the multiple PDUS may constitute a completeSDU. That is, the SDU data may be generated by at least one PDU, whichis capable of constituting a complete SDU, and a previous (and/orposterior) PDU of the at least one PDU.

For example, if the receiving end receives PDU 1, PDU 2 and PDU 3, whichconstitute a complete SDU, the receiving end may perform de-headerprocessing on the PDU 1. PDU 2 and PDU 3 and generate a complete SDU.

Alternatively, if the receiving end receives PDU 4, PDU5 and PDU 6, thePDU 5 is a complete SDU (denoted as SDU1), the PDU 4 and PDU 6 may besegments of other SDUs other than SDU1, the PDU 4 and PDU 6 may belongto a same SDU or may belong to different SDUs, then the receiving endmay also perform de-header processing on the PDU 4, PDU 5 and PDU 6 togenerate an SDU.

In the first delivery mode, after the SDU data is generated, thereceiving end directly delivers the SDU data to the upper layer, even ifprevious SDU data of the SDU data has not been delivered to the upperlayer. That is, the receiving end can disorderly deliver the SDU data tothe upper layer.

In the second delivery mode, after the SDU data is generated, thereceiving end needs to wait for all previous SDU data of the SDU dataare delivered to the upper layer, and then before the SDU data can bedelivered to the upper layer. That is, the receiving end needs todeliver SDU data to the upper layer in order.

The method embodiments of the present application are described indetail above with reference to FIGS. 2 to 4. Hereinafter, deviceembodiments of the present application will be described in detail withreference to FIGS. 5 to 8. It should be understood that the deviceembodiments and the method embodiments correspond to each other, andsimilar descriptions can refer to the method embodiments.

FIG. 5 is a schematic block diagram of a device for transmitting dataaccording to an embodiment of the present application. The device 400 ofFIG. 5 includes:

a processing module 410, configured to start a timer of a first deliverymode when determining that delivered data and data to be delivered arenot continuous, where the first delivery mode is used to indicate thatthe device directly delivers data to an upper layer upon receipt of thedata; and

a communicating module 420, configured to deliver the data to bedelivered to the upper layer using the first delivery mode when thetimer of the first delivery mode does not expire.

In some embodiments, the processing module 410 is further configured to:

stop the timer of the first delivery mode when determining that thedelivered data and the data to be delivered are continuous, if the timerof the first delivery mode is running.

In some embodiments, the device further includes:

a determining module, configured to determine whether the delivered dataand the data to be delivered are continuous according to windowinformation of a reordering window and information of the delivereddata.

In some embodiments, the window information of the reordering windowincludes a window lower bound identification of the reordering window,and the determining module is specifically configured to:

determine whether the delivered data and the data to be delivered arecontinuous according to the window lower bound identification of thereordering window and a serial number SN of a last delivered servicedata unit SDU.

In some embodiments, the determining module is specifically configuredto:

determine that the delivered data and the data to be delivered are notcontinuous if a count value corresponding to the window lower boundidentification is not equal to a count value corresponding to a next SNof the SN of the last delivered SDU; or

determine that the delivered data and the data to be delivered arecontinuous if the count value corresponding to the window lower boundidentification is equal to the count value corresponding to the next SNof the SN of the last delivered SDU,

In some embodiments, the processing module 410 is further configured to:

set a window lower bound identification of a reordering window to acount value corresponding, to an SDU that is expected to be deliverednext time when the timer of the first delivery mode is in an expiredstate.

In some embodiments, the processing module 410 is further configured to:

start the timer of the lust delivery mode when the count valuecorresponding to the SDU that is expected to be delivered next time isnot equal to the count value corresponding, to the last delivered SDUdelivered last time.

In some embodiments, the device is a terminal device or a networkdevice.

In some embodiments, the device is a terminal device, and thecommunicating module 420 is further configured to:

receive indication information sent by a network device, where theindication information is used to indicate that the device delivers datato the upper layer using the first delivery mode or a second deliverymode, where the second delivery mode is used to indicate that the devicedelivers data to the upper layer in order.

In some embodiments, the indication information is specificallyconfigured to indicate that a packet data convergence protocol PDCPlayer of the device delivers data to the upper layer using the firstdelivery mode or the second delivery mode.

In some embodiments, the indication information is specificallyconfigured to indicate that a radio link control RLC layer of the devicedelivers data to the upper layer using the first delivery mode or thesecond delivery mode.

In some embodiments, communicating module 420 is specifically configuredto:

receive a radio resource control RRC signaling sent by the networkdevice, where the radio resource control signaling includes theindication information.

In some embodiments, the communicating module 420 is specificallyconfigured to:

receive a media access control MAC control element CE or a packet dataconvergence protocol PDCP control protocol data unit PDU, sent by thenetwork device, where the MAC CE or PDCP control PDL I includes theindication information.

Specifically, the device 400 may correspond to (e.g., may be configuredat or be itself) the receiving end described in the above method 200. Inaddition, modules or units in the device 400 are respectively configuredto execute the actions or processing procedures executed by thereceiving end in the above method 200. Here, detailed descriptionthereof will be omitted to avoid repetition.

FIG. 6 is a schematic block diagram of a device for transmitting dataaccording to an embodiment of the present application. The device 500 ofFIG. 6 includes:

a setting module 510, configured to set a duration of a timer of asecond delivery mode to zero; and

a communicating module 520, configured to deliver data to be deliveredto an upper layer using a first delivery mode;

where the first delivery mode is used to indicate that the devicedirectly delivers the data to the upper layer upon receipt of the data,and the second delivery mode is used to indicate that the device todelivers data to the upper layer in order.

Specifically, the device 500 may correspond to (e.g., may be configuredat or be itself) the receiving end described in the above method 300. Inaddition, modules or units in the device 500 are respectively configuredto execute the actions or processing procedures executed by thereceiving end in the above method 300. Here, detailed descriptionthereof will be omitted to avoid repetition.

FIG. 7 is a schematic block diagram of a terminal device fortransmitting data according to an embodiment of the present application.The terminal device 800 of FIG. 7 includes:

a communicating module 810, configured to receive indication informationsent by a network device, where the indication information is used toindicate that a packet data convergence protocol PDCP layer and a radiolink control RLC layer of the terminal device deliver data to an upperlayer using a first delivery mode or a second delivery mode, where thefirst. delivery mode is used to indicate that the terminal devicedirectly generates service data unit SDU data and deliver the SDU datato the upper layer upon receipt of protocol data unit PDU data, and thesecond delivery mode is used to indicate that the terminal devicedelivers data to the upper layer in order; and deliver the SDU data tothe upper layer according to the indication information.

Specifically, the terminal device 800 may correspond to (e.g., may beconfigured at or be itself) the receiving end described in the abovemethod 700. In addition, modules or units in the terminal device 800 arerespectively configured to execute the actions or processing proceduresexecuted by the terminal device in the above method 700. Here, detaileddescription thereof will be omitted to avoid repetition.

As shown in FIG. 8, an embodiment of the present application furtherprovides a device 600 for transmitting data. The device 600 can be thedevice 400 in FIG. 5, or the device 500 in FIG. 6, or the device 800 inFIG. 7, which can be configured to execute the content of the receivingend corresponding to the method 200 in FIG. 2, or the method 300 in FIG.3. or the content of the terminal device corresponding to the method 700in FIG. 4. The device 600 includes: an input interface 610, an outputinterface 620, a processor 630 and a memory 640, the input interface610, output interface 620, processor 630 and memory 640 can be connectedthrough a bus system. The memory 640 is configured to store programs,instructions or codes. The processor 630 is configured to execute theprograms, instructions or codes in the memory 640 to control the inputinterface 610 to receive a signal, control the output interface 620 tosend a signal, and complete the operations in the foregoing methodembodiments.

It should be understood that in the embodiments of the presentapplication, the processor 630 may be a Central Processing Unit (CPU)and the processor 630 may also be other general purpose processors,digital signal processors (DSPs), application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs) or otherprogrammable logic devices, discrete gates or transistor logic devices,discrete hardware components, and the like. The general purposeprocessor may be a microprocessor or the processor may also be anyconventional processors, and the like.

The memory 640 may include a read only memory and a random accessmemory, and provide instructions and data to the processor 630. Aportion of memory 640 may also include a non-volatile random accessmemory. For example, the memory 640 may also store device typeinformation.

During an implementation, contents of the above method can be completedby an integrated logic circuit of hardware or instructions in the formof software in the processor 630. The content of the method disclosed inconnection with the embodiment of the application may be directlyimplemented by a hardware processor, or in the combination of hardwareand software modules in the processor. Software modules can be locatedin mature storage media in the art, such as a random access memory, aflash memory, a read only memory, a programmable read only memory or anelectrically erasable programmable memory, a register, and the like. Thestorage medium is located in the memory 640. The processor 630 reads theinformation in the memory 640 and completes the contents oldie abovemethod with reference to its hardware, which will not be described indetail herein to avoid repetition.

In a specific embodiment, the processing module 410 included in thedevice 400 in FIG. 5 may be implemented by the processor 630 in FIG. 8,and the communicating module 420 included in the device 400 in FIG. 5may be implemented by the input interface 610 and the output interface620 in FIG. 8.

In another specific embodiment, the setting module 510 included in thedevice 500 in FIG. 6 may be implemented by the processor 630 in FIG. 8,and the communicating module 520 included in the device 500 in FIG. 6may be implemented by the input interface 610 and the output interface620 in FIG. 8.

In a further specific embodiment, the communicating module 810 includedin the device 800 in FIG. 7 may be implemented by the input interface610 and the output interface 620 in FIG. 8.

An embodiment of the present application further provides a computerreadable storage medium storing one or more programs, where the one ormore programs include instructions, which, when executed by a portableelectronic device including multiple applications, enable the portableelectronic device to execute the methods of the embodiments shown inFIGS. 2 to 4.

An embodiment of the present application further provides a computerprogram including instructions, which, when executed by a computer,enable the computer to execute the corresponding flow of the methods ofthe present embodiments shown in FIGS. 2 to 4.

Those skilled in the art will appreciate that the elements and algorithmsteps of the examples described in conjunction with the embodimentsdisclosed herein can be implemented in electronic hardware or acombination of computer software and electronic hardware. Whether thesefunctions are performed in hardware or software, it depends on specificapplications and design constraints of the technical solution. A personskilled in the art may use different methods to implement the describedfunctions with respect to each particular application, but suchimplementation should not be considered to go beyond the scope of thepresent application.

Those skilled in the art can clearly understand that, for convenienceand brevity of the description, for specific operation processes of thesystems, the apparatuses and the units described above, reference may bemade to the corresponding processes in the above method embodiments, anddetails will not be described herein again.

In the embodiments provided in the present application, it should beunderstood that the disclosed systems, apparatuses, and methods may beimplemented in other manners. For example, the apparatus embodimentsdescribed above are merely illustrative. For example, the division ofthe units is only a logical function division. In an actualimplementation, there may be another division manner. For example,multiple units or components may be combined or may be integrated intoanother system, or some features may be ignored or not executed. Inaddition, a coupling or direct coupling or communication connectionshown or discussed may be an indirect coupling or communicationconnection through some interfaces, apparatuses or units, and may beelectrical, mechanical or otherwise.

The units described as separate components may or may not be physicallyseparated, and the components shown as units may or may not be physicalunits, that is, may be located in one place, or may be distributed tomultiple network units. Some or all of the units may be selectedaccording to actual needs to achieve the purpose of the solutions of theembodiments.

In addition, the functional units in the embodiments of the presentapplication may be integrated into one processing unit, or each of theunits may exist alone physically, or two or more units may be integratedin one unit.

The functions may be stored in a computer readable storage medium ifimplemented in the form of a software functional unit and sold or usedas a standalone product. Based on such understanding, the essence of thetechnical solution of the present application, or a part of thetechnical solution of the present application contributing to the priorart, or a part of the technical solution may be embodied in the form ofa software product which is stored in a storage medium, includinginstructions for enabling a computer device (which may be a personalcomputer, a server, or a network device, etc.) to perform all or part ofthe steps of the embodiments of the present application. The abovestorage medium includes: various mediums capable of storing programcodes, such as a USB Rash disk, a mobile hard disk., a read-only memory(ROM), a random access memory (RAM), a magnetic disk, an optical disk,or the like.

The above description is only specific embodiments of the presentapplication, but the protection scope of the present application is notlimited thereto. Any modification or the substitution conceived bypersons skilled in the art within the technical scope of the presentapplication should be covered in the protection scope of the presentapplication. Therefore, the protection scope of the present applicationis subject to the protection scope of the appended claims.

What is claimed is:
 1. A method for transmitting data, comprising:starting, by a receiving end, a timer of a first delivery mode whendetermining that delivered data and data to be delivered are out oforder, wherein the first delivery mode is used to indicate that thereceiving end directly delivers data to an upper layer upon receipt ofthe data, and delivering, by the receiving end, the data to be deliveredto the upper layer using the first delivery mode when the timer of thefirst delivery mode has not expired.
 2. The method of claim 1, furthercomprising: stopping, by the receiving end, the timer of the firstdelivery mode, when determining that the delivered data and the data tobe delivered are in order, if the timer of the first delivery mode isrunning.
 3. The method of claim 1, further comprising: determining, bythe receiving end, whether the delivered data and the data to bedelivered are in order according to window information of a reorderingwindow and information of the delivered data.
 4. The method of claim 1,further comprising: setting a window lower bound identification of areordering window to a count value corresponding to an SDU that isexpected to be delivered next time when the tinier of the first deliverymode is in an expired state.
 5. The method of claim 4, wherein thestarting, by the receiving end the timer of the first delivery mode whendetermining that the delivered data and the data to be delivered are outof order, comprises: starting the timer of the first delivery mode whenthe count value corresponding to the SDU that is expected to bedelivered next time is not equal to a next count value of the countvalue corresponding to a last delivered SDU.
 6. The method of claim 1,wherein the receiving end is a terminal device or a network device. 7.The method of claim 6, wherein the receiving end is a terminal device,and the method further comprises: receiving, by the receiving end,indication information sent by a network device, wherein the indicationinformation is used to indicate that the terminal device delivers datato the upper layer using the first delivery mode or a second deliverymode, wherein the second delivery mode is used to indicate that thereceiving end delivers data to the upper layer in order.
 8. The methodof claim 7, wherein the indication information is configured to indicateat least one of the following: a packet data convergence protocol (PDCP)layer of the terminal device delivers data to the upper layer using thefirst delivery mode or the second delivery mode; and a radio linkcontrol (RLC) layer of the terminal device delivers data to the upperlayer using the first delivery mode or the second delivery mode.
 9. Themethod of claim 7, wherein the receiving, by the receiving end, theindication information sent by the network device, comprises: receiving,by the receiving end, a radio resource control (RRC) signaling sent bythe network device, wherein the radio resource control signalingcomprises the indication information.
 10. A device for transmittingdata, comprising: a memory, a processor, a transceiver and a computerprogram stored on the memory and operable on the processor, wherein theprocessor, when running the computer program, is configured to: start atimer of a first delivery mode when determining that delivered data anddata to be delivered are out of order, wherein the first delivery modeis used to indicate that the device directly delivers data to an upperlayer upon receipt of the data; and control the transceiver to deliverthe data to be delivered to the upper layer using the first deliverymode in a case wherein the timer of the first delivery mode has notexpired.
 11. The device according to claim 10, wherein the processor isfurther configured to: stop the timer of the first delivery mode, whendetermining that the delivered data and the data to be delivered are inorder, if the timer of the first delivery mode is running.
 12. Thedevice according to claim 10, wherein the processor is fartherconfigured to: determine whether the delivered data and the data to bedelivered are in order according to window information of a reorderingwindow and information of the delivered data.
 13. The device of claim10, wherein the processor is configured to: set a window lower boundidentification of a reordering window to a count value corresponding toan SDU that is expected to be delivered next time when the timer of thefirst delivery mode is in an expired state.
 14. The device of claim 13,wherein the processor is further configured to: start the timer of thefirst delivery mode when the count value corresponding to the SDU thatis expected to be delivered next time is not equal to a next count valueof the count value corresponding to a last delivered SDU.
 15. The deviceof claim 10, wherein the device is a terminal device or a networkdevice.
 16. The device of claim 15, wherein the device is a terminaldevice, and the processor is configured to: control the transceiver toreceive indication information sent by a network device, wherein theindication information is used to indicate that the device delivers datato the upper layer using the first delivery mode or a second deliverymode, wherein the second delivery mode is used to indicate that thedevice delivers data to the upper layer in order.
 17. The device ofclaim 16, wherein the indication information is configured to indicatethat a packet data convergence protocol (PDCP) layer of the devicedelivers data to the upper layer using the first delivery mode or thesecond delivery mode.
 18. The device of claim 16, wherein the indicationinformation is configured to indicate that a radio link control (RLC)layer of the device delivers data to the upper layer using the firstdelivery mode or the second delivery mode.
 19. The device of claim 16,wherein the processor is configured to: control the transceiver toreceive a radio resource control (RRC) signaling sent by the networkdevice, wherein the radio resource control signaling comprises theindication information.
 20. A device for transmitting data, comprising:a memory, a processor, and a computer program stored on the memory andoperable on the processor, wherein the processor, when running thecomputer program, is configured to: set a duration of a timer of asecond delivery mode to zero; and deliver data to be delivered to anupper layer using a first delivery mode wherein the first delivery modeis used to indicate that the device directly delivers data to the upperlayer upon receipt of the data, and the second delivery mode is used toindicate that the device delivers data to the upper layer in order.